JavaScript Debugger Modules > What is a JavaScript Debugger Module? > The JavaScript Debugger Module API |
![]() ![]() ![]() |
The JavaScript Debugger Module API
The JavaScript Debugger Module API allows you to customize the way the debug version of a document is created. You would need to create a debugger module if you wanted to make the Dreamweaver JavaScript Debugger work with a browser other than the two (Netscape and Internet Explorer) for which Dreamweaver already provides support. You could also create a debugger module for some other specialized purpose, such as counting the number of JavaScript statements used by a particular document.
Note: Currently only SCRIPT tags and event handlers are parsed for instrumentation. There are some other ways to use JavaScript in HTML documents, such as JavaScript URLs, JavaScript entities, and conditional comments. These are not currently supported.
The JavaScript Debugger Module API functions are significant only in the context of debugger module files. Specifically, Dreamweaver automatically calls the getStepInstrument()
function if it is defined in the debugger module file. For any other extension file, a function named getStepInstrument()
acts like a user-defined functionyou have to call it explicitly.
As opposed to the way you work with the functions in the main JavaScript API, you are responsible for writing the body of each function and returning a value, if required, for the debugger modules. For the functions in the main API, you call and pass arguments, and Dreamweaver generates return values, if any. For the debugger modules, Dreamweaver calls the functions and passes arguments to them, and you generate return values, if any.
All of the JavaScript Debugger Module functions are optional. If a function is not defined, then nothing happens when Dreamweaver calls it.
![]() ![]() ![]() |